home *** CD-ROM | disk | FTP | other *** search
- NetWare Client for OS/2 2.1
- ReadMe File
- April 14, 1994
-
- Please email any comments or suggestions to os2req@novell.com.
-
- NOTE: Full trademark attributions are listed in the documentation with
- this product.
-
- VERSION 2.10 ENHANCEMENTS AND IMPROVEMENTS
- The NetWare Client for OS/2 manual and selected NetWare utilities references
- are now provided as on line documentation. See the icons in the Novell
- folder on the OS/2 desktop.
-
- This version replaces OS/2 Requester Version 2.01 and is qualified
- with:
- OS/2 Version 2.10
- OS/2 for Windows Version 2.1 (see special instructions under
- NetWare for OS/2 "OS/2 for Windows Installation")
- NetWare 2.15c and NetWare 2.2
- NetWare 3
- SFT III
- NetWare 4
-
- NetWare Client for OS/2 Version 2.10 provides/supports:
- 100% DOS NETX 3.32 compatability
- Enhanced mode MS Windows applications
- RPL (Remote Program Load)
- User configurable default login drive
- Redirection of up to nine (9) parallel ports under an OS/2 session
-
-
- INITIAL INSTALLATION
- Since NetWare DLLs are not included in the LIBPATH in a new installation,
- you must first change to the drive that contains the NetWare installation
- files before executing the "INSTALL" command. Once you've changed to the
- drive, then type "INSTALL".
-
- For example, if you are installing from diskettes in the a: drive,
- first type "a:". Once the A: prompt is displayed, then type
- "INSTALL".
-
- Third Party Drivers with a Network Installation
- If you are installing NetWare Client for OS/2 from a network and
- you are using third party drivers, you must first copy the drivers to
- the OS2 directory under the network install directory before you
- begin the installation program. The OS2 and the root directory
- of the source install are the only locations where the installation
- program looks to find the drivers.
-
-
- OS/2 CONFIG.SYS
- Previous versions of the NetWare statements in the CONFIG.SYS
- may not be compatible with NetWare Client for OS/2 2.10.
- Be sure to choose "Edit CONFIG.SYS and Copy All Files" from the
- Requester Installation window. This is the default option of
- the installation utility. Choosing this option will ensure that
- proper paths will be setup and drivers will be loaded in the
- correct order in the CONFIG.SYS.
-
- NETX
- All DOS sessions require NETX now. NETX uses 49.9K of memory.
-
- DOS_LASTDRIVE
- The DOS_LASTDRIVE property must be set to a drive letter other
- than Z (the default). Usually, this is set to the last local drive
- letter available on the client workstation. (See the on line document
- for information on how to change the DOS_LASTDRIVE setting.)
-
- Loading NETX in Upper Memory
- Loading NETX in upper memory provides more memory for DOS
- applications with large memory needs. The default setting does
- not load NETX in upper memory blocks. For NETX to load in the
- upper memory blocks, the following DOS_SETTINGS need to be
- manipulated:
-
- DOS_UMB set to ON
- DOS_HIGH set to ON (optional)
- EMS_FRAME_LOCATION set to NONE
-
- Use the DOS LOADHIGH command to load NETX into upper
- memory.
-
- When you type CLS in a DOS Session with NETX loaded, these
- characters may display: <-{2J. Load ANSI.SYS in the
- CONFIG.SYS to resolve this issue.
-
- Capturing Printer Ports in DOS Sessions
- In global DOS sessions, capturing to a printer port is now local to
- the DOS session in which the capture occurs.
-
- Global DOS Connection Support
- DOS sessions will support only up to eight connections. Any
- connection after that will be seen only under OS/2 sessions.
-
- Extended Attributes (EA) Support
- EAs are not supported in private and global DOS sessions.
- To copy files containing EAs, use NCOPY or OS2-based utilities
- in an OS/2 session.
-
- IBM DOS Support Issues
- After NETX loads high, no other TSRs can be loaded high. IBM is
- currently fixing the problem. To the best of our knowledge, no
- release dates have been given.
-
- Due to DOS emulation incompatabilities, the following utilities
- will not function correctly under DOS sessions:
- ATTRIB
- MENU
- Please use OS/2 sessions to run these utilities.
-
-
- NETWARE 2.15c AND NETWARE 2.2 SUPPORT
- NetWare 2.15c and NetWare 2.2 do not support Extended Attributes
- or Name Spaces. Consequently, OS/2 support for these features
- is limited under these two versions of NetWare. REXX files and
- files created by the OS/2 Editor use Extended Attributes and are not
- supported by these versions of NetWare. Similarly, other files that use
- Extended Attributes are not supported. Additionally, if you
- need OS/2 HPFS support on your network, you will need to use a
- NetWare 3 or NetWare 4 network operating system.
-
-
-
- KNOWN PROBLEMS
- Problems in DOS Sessions with Pentium Processors
- Private and global DOS sessions using Pentium processors may
- not function properly. Novell has been unable to reproduce this
- problem in our initial testing of OS/2 version 2.11.
-
- DOS Commands Under OS/2
- Do not issue DOS commands in an OS/2 session. Doing this
- gives unknown/undetermined problems in global OS/2 and global
- DOS sessions.
-
- Installing Over Existing OS/2 Requester 2.0
- When attempting to install NetWare Client for OS/2 2.1 over the
- OS/2 Requester 2.0, the following error will occur: "The operating
- system cannot run install->NWCALLS-182." In order to get around
- this issue, remove all references to the NetWare Requester from
- the path statements and the bottom portion of the OS/2 CONFIG.SYS.
- Reboot the machine. Then, delete the directory containing
- the requester files. You can now run the NetWare Client for OS/2
- 2.1 installation program.
-
- Remapping the C: Drive in Remote (RPL) Workstations
- Mapping the RPL drive in a global DOS session will not affect any
- drive mappings in any other DOS or OS/2 session.
-
- CTRL-C
- Some NetWare utilities will trap the session when the user
- presses CTRL-C. Please contact your IBM representative and refer
- to IBM APAR # PJ10994.
-
- Named Pipes
- Heavy usage of Named Pipes might cause a trap in the OS/2
- kernel. Please contact your IBM representative and refer to
- IBM APAR # PG12344.
-
- NPRINTER
- If NPRINTER is printing and you choose to terminate NPRINTER.EXE,
- your workstation might hang.
-
- LPT Redirection in DOS Global Sessions
- If you capture LPT1-LPT3 in OS/2 sessions, those captures are
- automatically available in DOS global sessions. If you want to change
- the capture available to the DOS global session, this can be done by
- running a DOS capture in that session. That capture would
- be unique to that session. If you are running a DOS capture in your
- global sessions and using OS/2 2.1, load ANSI.SYS under the
- DOS_DEVICES in the DOS Notebook settings. This will ensure
- that the print job will capture to the queue correctly. This issue has
- been addressed in OS/2 2.11.
-
- LPT Redirection in OS/2 Sessions
- OS/2 is designed such that when redirecting files to LPT4 through LPT9,
- the following syntax must be used.
-
- COPY {filename} \DEV\LPT#
-
-
- NEWER UTILITIES
- You need a new SYSCON.EXE for OS/2 sessions. The install program
- will not copy this automatically. Your System Administrator needs to
- update to the new utilities from the accompanying diskette labelled
- "Newer Utilities".
-
-
- RPL
- Enhanced Boot PROMs may cause a Remote Program Load (RPL)
- workstation to hang when used with NetWare routers. The problem
- can be avoided by reconfiguring the server running RPL.NLM. Have
- your System Administrator add the 'PS=' parameter to the
- BIND RPL statement.
-
- For example:
- BIND RPL to TOKEN PS=<your server name>
-
- This problem is fixed in NetWare 4.1 and following.
-
- If a file has trouble copying, it could be because it has more extended
- attributes than the server is set to handle. Increasing the "Maximum
- Extended Attributes per File or Path" setting on your server should solve
- this issue.
-
-
- OS/2 FOR WINDOWS INSTALLATION
- If the original NETWARE.DRV file on your workstation is for
- NetWare 4.x, it will be renamed as NETWARE.NDS during the NetWare
- Client for OS/2 installation. If you want to boot your workstation
- using NetWare 4.x support under regular DOS, the NetWare 3.x version
- of NETWARE.DRV needs to be saved and the NETWARE.NDS version needs
- to be renamed NETWARE.DRV.
-
-
- DOS/WINDOWS APPLICATION ISSUES
- Unless otherwise stated, the following switches are suggested:
- -ALL Applications
- DOS_DEVICE = D:\OS2\MDOS\LPTDD.SYS
- Required for any device that prints to Parallel Ports.
- DOS_FILES >= 120
- Needed for most Database applications/Safe default.
- DOS_HIGH = ON
- Leaves more usable memory for applications.
- DOS_UMB = ON
- Leaves more usable memory for applications.
- DPMI_DOS_API = ENABLED
- Many applications (such as those using Borland APIs) require
- this parameter to be enabled. All MS Windows 3.1 applications
- use DPMI.
- HW_ROM_TO_RAM = ON
- Improves speed of applications with minimal impact on
- available memory.
- IDLE_SENSITIVITY <= 25
- This is a problem with the OS/2 task switcher
- algorithm. With the default of 75 some applications may
- appear to hang when in fact they are just running
- EXTREMELY slow.
- INT_DURING_IO = OFF
- Unless your application is a Multi-media application that
- needs to drive a video display or a speaker while reading
- a CD-ROM or hard drive, it is strongly suggested that
- this switch remains off. IF YOUR APPLICATION IS NOT
- WRITTEN TO EXPECT INTERRUPTS DURING I/O THIS
- SWITCH MAY CAUSE YOUR APPLICATION OR MACHINE
- TO HANG OR DESTROY DATA ON DISK.
-
- -MS Windows Applications (MS Windows Defaults)
- VIDEO_8514A_XGA_IOTRAP = OFF
- Set this to off unless your program expects to use the
- 8514a or XGA video modes. Setting this to off will free
- 1MB of memory and speed up all MS Windows and most
- DOS applications.
- VIDEO_RETRACE_EMULATION = OFF
- Since MS Windows is a graphical interface this switch
- will improve the application's performance.
- VIDEO_SWITCH_NOTIFICATION = ON
- This is insurance against applications switching to
- 8514a or XGA modes. With VIDEO_8514A_XGA_IOTRAP
- set to off, switching to 8514a or XGA may cause
- problems unless this switch is on. If the video mode
- changes windows needs to repaint itself and may not
- always detect the correct video mode, this should
- correct this problem also.
- DPMI_MEMORY_LIMIT >= 4096
- Most MS Windows applications will run better with 4mb
- or more of RAM.
-
- *Ascend
- Must run in full screen winos2.
- COM_DIRECT = ON (For Modem access)
- DPMI_MEMORY_LIMIT >= 4
- *Borland C/C++ 3.1
- - MS Windows API
- MS Windows system directory must be in path.
- DPMI_DOS_API = ENABLED
- - Debugger
- COM_DIRECT = ON
- *Clipper 5.x
- XMS_MEMORY_LIMIT >= 2048
- *DaVinci Email
- (MS Windows Defaults)
- *dBase IV 2.0
- (Defaults)
- *Excel 4.0
- VIDEO_8514A_XGA_TRAP = OFF
- VIDEO_RETRACE_EMULATION = OFF
- VIDEO_SWITCH_NOTIFICATION = ON
- DPMI_MEMORY_LIMIT >= 4096
- *Foxpro 2.5
- WIN_RUN_MODE = Standard
- DOS_FILES >= 160
- DPMI_MEMORY_LIMIT >= 6
- *OnTime
- (MS Windows Defaults)
- *Lotus Notes
- (MS Windows Defaults)
- *Microsoft SQL Server
- (DOS Defaults)
- *Paradox 3.5/4.0
- (DOS Defaults)
- *Visio 1.0
- DPMI_DOS_API = ENABLED
- VIDEO_8514A_XGA_TRAP = OFF
- VIDEO_RETRACE_EMULATION = OFF
- VIDEO_SWITCH_NOTIFICATION = ON
- XMS_MEMORY_LIMIT >= 4096 (Minimum for printing to work)
- *Word for Windows 2.0a
- (MS Windows Defaults)
- *WordPerfect 6.0 for Windows
- WIN_RUN_MODE = Enhanced Compatiblity
- IDLE_SENSITIVITY = 100 (Disable idle detection)
- DPMI_MEMORY_LIMIT >= 6 (Less memory impedes performance)
-
-
- Please email any comments or suggestions to os2req@novell.com.